Repository navigation
improvement(search): steer Confluence native queries to siteSearch for topic lookups - #9742
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
 [Low impact] The PR appears safe to merge. SummaryUpdates the Confluence query guide to favor
Reviews (2) · Last reviewed commit: "improvement(search): describe text ~ as ..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 1 file
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
Collaborator
Author
Collaborator
Author
|
@cubic-dev-ai review this PR |
Contributor
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
text ~/title ~, so assistants searching Confluence directly wrote ORedtext ~clauses. CQL returns those in no relevance order, which puts pages sharing one common word (e.g. an acronym mentioned in passing) ahead of the page about the topic.siteSearch ~, Confluence's relevance search, for topic, acronym and how-to lookups, and keepstext ~/title ~for exact strings. The example and the avoid line follow.siteSearchon overflow; native queries skip that fallback, so the guide is the only lever on that path.Type of Change
Testing
text ~/title ~) and rewritten as onesiteSearchover the same words; a model judge compared the top 5 for the user's question in both orders, counting a win only when both orders agreed.siteSearchwon 21,text ~won 1, 18 ties (34/40 order-consistent).text ~returned nothing in 4 cases wheresiteSearchreturned 5. The one loss was an exact identifier lookup, which the guide still routes totext ~.type IN (page, blogpost) AND siteSearch ~ "<words>"put the page about the topic first in five; the ORedtext ~form led with pages that only mention a term. One was mixed (a short token fuzzy-matched a longer one).siteSearchqueries run through the existing native-CQL path unchanged (scope, pagination, page mapping).vitestonproviders.test.ts,application.test.ts,atlassian.test.ts: 117 passed.biome checkon the changed file.Checklist
test-auditauthoring gate)